Comparison of Software Requirements Tools
Mahalakshmi. R1*, Saranya. R1
1M.S (Software Engineering), VIT University, Vellore
*Corresponding Author E-mail: mahalakshmi.r2013@vit.ac.in, saranyar.2013@vit.ac.in
Abstract:
Requirements management is a critical and essential phase for the delivery of the product to be successful. The requirements can be called as user needs or desired feature for a product. So, only with well defined requirements, the products can achieve success. To collect well defined requirements and to manage the specified requirements we make use of requirements management tools. The objective of this paper is to present the comparative study on different requirements tools that are available and to determine the most essential tool.
KEY WORDS:
INTRODUCTION:
In the field of software engineering, requirements are the needs of the user that must be correctly managed and specified. In this paper we have presented the different requirements tools that can be used and well managed as per the requirements specified. A comparative study has been made to determine the top management tool that fulfills user needs.
“Automating Requirements Management” compared the tools like DOORS, RTM workshop, caliber-RM, and Requisitepro and the features they have in common are they parse a source document to load requirements into database, define different attributes for different types of requirements, define traceability relationships, usability options and includes threaded discussions and tool learning aids[1].
According to author Muhammad Said, “An Evaluation of Requirements Management and Traceability Tools” evaluated eleven requirements management and requirements traceability tools. The analysis summarize that requirements tools are used more instead of traceability tools. And they concluded that DOORS tool has most specifications features among the tools compared[2].Another one said that “Selecting Appropriate Requirements Management Tool for Developing Secure Enterprises Software”, compared cradle, caliber-RM, analyst pro, CORE analyzed that caliber RM tool comes out in front with tying between cradle and analyst pro[3].
Matthias Heindl, Franz Reinisch, Stefan Biffl, Alex Egyed,” Value-Based Selection of Requirements Engineering Tool Support”, reported on a value-based requirements tool selection approach developed at PSE that helps to find the optimal tool support and evaluated how existing requirement tools meet the needs for requirements tool support[8].Aurora Vizcaino, in their article “Requirements engineering tools: Capabilities, survey and assessment”, states that some enhancements to be made in order to make tool support some features that are located in requirements modeling, management
and some other capabilities. They also analyzed that modeling score lower than management and other capabilities. The theory that Re tools are more oriented towards natural language than towards modeling like UML etc. Also, the lack of open data model has been detected[5].
Tony Cant, Jim McCarthy and Robyn Stanley,” Tools for Requirements Management: a Comparison of Telelogic DOORS and the HIVE”, stated the integration of DOOR and Hive. Document production, data views, requirements and modeling, extendability are compared. Hive adds real value to front end and DOORS tool has been used to effect for this requirements listing and tracking. The comparison highlighted the innovative advantage of hive makes this an essential tool[7].
Rajat R. Sud and James D. Arthur define “Requirements Management Tools A Qualitative Assessment” presented a comparative study of requirements tools like rational suite analyst studio, RDT3.0, teleogic doors, caliber RM based on the features and capabilities[4]. Juan M. Carrillo de Gea, Joaquín Nicolás, José L. Fernández Alemán, Ambrosio Toval, Christ of Ebert, Aurora Vizcaíno” Requirements engineering tools: Capabilities, survey and assessment” in their article conducted a survey to gain an insight into how current RE tools support the RE process by means of concrete capabilities, and to what degree. The RE process seems to be well covered by current RE tools, but there is still a certain margin for amelioration, principally with regard to requirements modelling, open data model and data integration features [9].
According to TSSR,A Proposed Tool for Secure Software Requirement Management” evaluvated the requirements using a tool called Tool for secure software environment risk analysis, system requirements, security of the system and project, users/group restriction, encrypted database, and traceability. There are variety of tools available but for secure software development only a few tools are helpful[10]. Another literature Anthony Finkelstein & Wolfgang Emmerich, conveyed “The Future of Requirements Management Tools”, prospects different tools and distinguish developments that are in short term, medium term and future as well. Convergence of tools, robustness, tool integration are identifies as short term, web integration and multimedia in medium term, workflow, modeling and corporate management have been identified in long term. They state that requirements tools are the heart of the system engineering[6].Matthias Hoffmann, Nikolaus Kühn, Margot Bittner, “Requirements for Requirements Management Tools “ ,contributed the users to compare and select requirements management tools as well as helping tool providers to direct future tool developments. It also covers the core functions such as information model, baselining, and tracebility and so on[11].Many Browning, J. and Adams, R. (2014) Doorstop: Text Based Requirements Management Using Version Control. Journal of Software Engineering and Applications, in this journal provided an alternative to traditional requirements management called Doorstop was created as a tool to allow requirements to be stored as text files in version control[12].
The existing systems have compared the requirements engineering tools like DOORS, RequisitePro, and Caliber-RM, RTM workshop, cradle and concluded that requirements modeling tools are less used than requirements management tools. The tools considered are almost the same in all papers.
The different features are analyzed for these tools. The essential RE tool has to be selected based on the requirements of the user is the conclusion that papers have given.
Vendors and operators have to work hard with the highest efficiency and effectiveness .Requirements management tools helps to achieve this goal. As there are different tools suitable for different systems and industry, we are focusing on tools that support requirements management and trace requirements links between different artifacts.In the proposed system, we are going to compare different set of tools that are not compared in the above papers. Different tools have different features and functions. Requirements tools like top team, Caliber RM, Rational Doors, Requirements composer, cradle, requistie. The features that these tools support in common and their differences are identified. The comparative study has been made to determine the essential requirements tool that tops among the selected tools. We believe, these are the best criteria to test the requirements management tools.
ARCHITECHTURE DIAGRAM:
OVERVIEW OF REQUIREMENT TOOLS:
There are huge number of requirement management tools which exists in literarture. Here we present some of the tools which are most likely used in many areas.We present their various supporting features of each tool which is helpful for any requirement manager to choose the appropriate tool.
The list of tools are discussed below:
Caliber RM is a requirement management tool initially developed by Borland. It is designed to facilitate collaboration, impact analysis, and communication process.
It keeps a record changes ,so it is possible to go back and see what the changes have been made to the requirements.
Features:
Ø Centralized repository-This Provides central, secure repository where the requirements are stored,and the people can fetch at any point of time.
Ø Adaptable-It is built to provide efficient speed and agility to the requirement process.
Ø Defines terminology-terminology helps to refine requirements on the way, so it does not become costly when finding defects in later stages.
Cradle is requirements management tool which integrate your
Overall project lifecycle into one massive, multi-user product.
It delivers outstanding improvements in interoperability, management and cost savings.
Features:
Ø Process support-Embed your process in to cradle UI, and thus reduces the need for training.
Ø Baselines and change control-supports evolution of database content through integral configuration management and control system with full change lacking of all edits.
Ø Progress tracking and metrics-provides built in metrics support to track all project activities and products.
IBM Rational Requisite Pro provides requirements management, traceability, and impact analysis capabilities for project teams, primarily suited to organizations creating application software. This also helps project teams to manage their requirements, to write good use cases, to improve traceability, to strengthen collaboration, to reduce project rework, and to increase quality
Features:
Ø Achieve collaboration for geographically distributed teams.
Ø Improve productivity by tracking changes using project version comparisons with XML-based project baselines.
Ø Manage complexity with detailed traceability views.
Ø Avoid rework and duplication using advanced, real-time integration with Microsoft Word.
IBM Rational DOORS software is the market leading requirements management application that can help you reduce costs, increase efficiency and improve quality by enabling you to optimize requirements communication, collaboration and verification — throughout your organization and across your supply chain. It includes proven capabilities that can help increase quality and efficiency by optimizing requirements communication and collaboration and ensures scalable solution for managing project scope and cost, helps your projects meet business goals, satisfy customer needs, and address applicable regulations and standards.
Features:
Ø Provides a comprehensive requirements management environment
Ø Manages changes to requirements with either a simple pre-defined change proposal system or a more thorough, customizable change control workflow through integration
Ø Allows stakeholders to contribute new requirements, analyze or elaborate on existing requirements, and validate a specification directly from their Web browser
Ø Provides fast and easy deployment to your user community - no software installation is required, all you need is a Web browser.
Reqsuite is a requirements engineering tool that does not only provide common Requirements Management features such as versioning, or tracing, but assistance functions to guide and support requirements elaboration activities .
Features:
Ø Context-sensitive guidance and hints during requirements elaboration
Ø Model-based configuration of requirements types
Ø Requirements reuse by copy and reference
Ø Exports to MS Word, MS Excel, JIRA.
TopTeam is a unique tool that enables various disciplines developed by technosolutions.This can be explained by the integral design that looks beyond the requirements. One of the easiest tool, with rich features "off the shelf", ensures that contribute to achieving the common objectives.
Features:
Ø powerful repository to document all kinds of information.
Ø Extensive features to document and manage requirements.
Ø Strong traceability functions and visualization.
Life cycle support with versioning, releases and baselines.
CONCLUSION:
In this paper we have analysed the commonly referrers software requirement tools .we have compared various tools features used by each tool. No tool supports full automated works some works has to be done manually for good presentation of requirements. Each and every tool has some strong and weak points.Rational DOORS supports most criteria and has best and wide benefits for requirement management tool. Because this tool satisfies both functional and non functional requirements .
As a result of our study, we suggest that there is a possibility of huge potential in this field to gather ,elicit and validate requirements. We hope the result will help developer to develop right tool to overcome drawbacks and benefits the developer to choose the most appropriate tool.
[1] Muhammad Shahid, Suhaimi Ibrahim, and Mohd Naz’ri Mahrin ,“ An Evaluation of Requirements Management and Traceability Tools”, World Academy of Science, Engineering and Technology International Journal of Computer, Electrical, Automation, Control and Information Engineering Vol:5, No:6, 2011
[2] Karl E. Wiegers, “Automating Requirements Management” , Process Impact.
[3] Rajat R. Sud and James D. Arthur in “Requirements Management Tools A Qualitative Assessment”, Department of Computer Science, Virginia Tech Blacksburg, VA 24060 USA
[4] Daniyal M Alghazzawi, Sham Tabrez Siddiqui, Mohammad Ubaidullah Bokhari, Hatem S Abu Hamatta, “Selecting Appropriate Requirements Management Tool for Developing Secure Enterprises Software”, I.J. Information Technology and Computer Science, 2014, 04, 49-55 Published Online March 2014 in MECS (http://www.mecspress.org/)DOI:10.5815/ijitcs.2014.04. 6
[5] Juan M. Carrillo de Gea , Joaquín Nicolás , José L. Fernández Alemán , Ambrosio Toval, Christof Ebert, Aurora Vizcaíno, “Requirements engineering tools: Capabilities, survey and assessment”, in press.
[6] Anthony Finkelstein & Wolfgang Emmerich, “The Future of Requirements Management Tools”, Information Systems in PublicAdministration and Law, Oesterreichische Computer Gesellschaft, 2000.
[7] Tony Cant, Jim McCarthy and Robyn Stanley,” Tools for Requirements Management: a Comparison of Telelogic DOORS and the HIVE”, Information Networks Division. Defence Science and Technology Organisation.
[8] Matthias Heindl, Franz Reinisch, Stefan Biffl, Alex Egyed,”Value-BasedSelectionofRequirementsengineeringtoolSupport”.
[9] Juan M. Carrillo de Gea, Joaquín Nicolás, José L. Fernández Alemán, Ambrosio Toval, Christof Ebert, Aurora Vizcaíno.
[10] Mohammad Ubaidullah Bokhari, Shams Tabrez Siddiqui,” TSSR: A Proposed Tool for Secure Software Requirement Management”.
[11] Matthias Hoffmann, Nikolaus Kühn, Margot Bittner” Requirements for Requirements Management Tools”.
[12] Browning, J. and Adams, R. (2014) Doorstop: Text-Based Requirements Management Using Version Control. Journal of Software Engineering and Applications.
Received on 04.05.2017 Modified on 20.05.2017
Accepted on 10.06.2017 ©A&V Publications All right reserved
Research J. Science and Tech. 2017; 9(2): 272-276.
DOI: 10.5958/2349-2988.2017.00049.3